MQTTConfig
MQTT Client Config
Content copied to clipboard
meshtastic.ModuleConfig.MQTTConfig
Types
Link copied to clipboard
class Builder : GeneratedMessage.Builder<BuilderT> , ModuleConfigProtos.ModuleConfig.MQTTConfigOrBuilder
MQTT Client Config
Content copied to clipboard
meshtastic.ModuleConfig.MQTTConfig
Properties
Functions
Link copied to clipboard
inline fun ModuleConfigProtos.ModuleConfig.MQTTConfig.copy(block: ModuleConfigKt.MQTTConfigKt.Dsl.() -> Unit): ModuleConfigProtos.ModuleConfig.MQTTConfig
inline fun ModuleConfigProtos.ModuleConfig.MQTTConfig.copy(block: ModuleConfigKt.MQTTConfigKt.Dsl.() -> Unit): ModuleConfigProtos.ModuleConfig.MQTTConfig
Link copied to clipboard
The server to use for our MQTT global message gateway feature.
If not set, the default server will be used
Content copied to clipboard
string address = 2;
Link copied to clipboard
The server to use for our MQTT global message gateway feature.
If not set, the default server will be used
Content copied to clipboard
string address = 2;
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
If a meshtastic node is able to reach the internet it will normally attempt to gateway any channels that are marked as
is_uplink_enabled or is_downlink_enabled.
Content copied to clipboard
bool enabled = 1;
Link copied to clipboard
Whether to send encrypted or decrypted packets to MQTT.
This parameter is only honoured if you also set server
(the default official mqtt.meshtastic.org server can handle encrypted packets)
Decrypted packets may be useful for external systems that want to consume meshtastic packets
Content copied to clipboard
bool encryption_enabled = 5;
Link copied to clipboard
Whether to send / consume json packets on MQTT
Content copied to clipboard
bool json_enabled = 6;
Link copied to clipboard
If true, we will periodically report unencrypted information about our node to a map via MQTT
Content copied to clipboard
bool map_reporting_enabled = 10;
Link copied to clipboard
Settings for reporting information about our node to a map via MQTT
Content copied to clipboard
.meshtastic.ModuleConfig.MapReportSettings map_report_settings = 11;
Link copied to clipboard
open fun getMapReportSettingsOrBuilder(): ModuleConfigProtos.ModuleConfig.MapReportSettingsOrBuilder
Settings for reporting information about our node to a map via MQTT
Content copied to clipboard
.meshtastic.ModuleConfig.MapReportSettings map_report_settings = 11;
Link copied to clipboard
Link copied to clipboard
MQTT password to use (most useful for a custom MQTT server).
If using a custom server, this will be honoured even if empty.
If using the default server, this will only be honoured if set, otherwise the device will use the default password
Content copied to clipboard
string password = 4;
Link copied to clipboard
MQTT password to use (most useful for a custom MQTT server).
If using a custom server, this will be honoured even if empty.
If using the default server, this will only be honoured if set, otherwise the device will use the default password
Content copied to clipboard
string password = 4;
Link copied to clipboard
If true, we can use the connected phone / client to proxy messages to MQTT instead of a direct connection
Content copied to clipboard
bool proxy_to_client_enabled = 9;
Link copied to clipboard
The root topic to use for MQTT messages. Default is "msh".
This is useful if you want to use a single MQTT server for multiple meshtastic networks and separate them via ACLs
Content copied to clipboard
string root = 8;
Link copied to clipboard
Link copied to clipboard
If true, we attempt to establish a secure connection using TLS
Content copied to clipboard
bool tls_enabled = 7;
Link copied to clipboard
MQTT username to use (most useful for a custom MQTT server).
If using a custom server, this will be honoured even if empty.
If using the default server, this will only be honoured if set, otherwise the device will use the default username
Content copied to clipboard
string username = 3;
Link copied to clipboard
MQTT username to use (most useful for a custom MQTT server).
If using a custom server, this will be honoured even if empty.
If using the default server, this will only be honoured if set, otherwise the device will use the default username
Content copied to clipboard
string username = 3;
Link copied to clipboard
Settings for reporting information about our node to a map via MQTT
Content copied to clipboard
.meshtastic.ModuleConfig.MapReportSettings map_report_settings = 11;
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
open fun parseDelimitedFrom(input: InputStream, extensionRegistry: ExtensionRegistryLite): ModuleConfigProtos.ModuleConfig.MQTTConfig
Link copied to clipboard
open fun parseFrom(data: Array<Byte>, extensionRegistry: ExtensionRegistryLite): ModuleConfigProtos.ModuleConfig.MQTTConfig
open fun parseFrom(data: ByteString, extensionRegistry: ExtensionRegistryLite): ModuleConfigProtos.ModuleConfig.MQTTConfig
open fun parseFrom(input: CodedInputStream, extensionRegistry: ExtensionRegistryLite): ModuleConfigProtos.ModuleConfig.MQTTConfig
open fun parseFrom(input: InputStream, extensionRegistry: ExtensionRegistryLite): ModuleConfigProtos.ModuleConfig.MQTTConfig
open fun parseFrom(data: ByteBuffer, extensionRegistry: ExtensionRegistryLite): ModuleConfigProtos.ModuleConfig.MQTTConfig
Link copied to clipboard
Link copied to clipboard